LOG

Section: Protocol Families (4F)
Updated: January 15, 1993
Index Return to Main Contents
 

NAME

log/* - session log files  

DESCRIPTION

Files in the etc/log directory in the FlexFAX spooling area contain logging/tracing information about transmit and receive sessions. One file exists for each machine, with the filename created from the remote machine's fully-qualified phone number. Transmit session tracing is placed in the file named by the destination phone number. Receive session tracing is placed in the file whose name is the ``local phone number''. The amount and kind of tracing information that is recorded is defined by the SessionTracing parameter specified in the modem configuration file; see config(4F).  

SERVER OPERATION

The following messages may appear when server operation tracing (bit 1) is enabled:

"MODEM: Unknown hint "%s" ignored".

"MODEM %s %s/%s".

"%s: Can not lock device.".

"%s: Can not open modem (%m)".

"%s: Can not open modem (timed out).".

"%s: setuid root failed (%m)".

"%s: fcntl: %m".

"%s: Can not deduce modem type.".

"RECV: Permission denied (unacceptable client TSI)".

"RECV: Unable to create file "%s" for received data".

"RECV data in "%s"".

"RECV: empty file "%s" deleted".

"ACCEPT TSI "%s"".

"REJECT TSI "%s"".

"POLL with CIG "%s"".

"POLL: Unable to create file "%s" for received data".

"POLL: empty file "%s" deleted".

"internal muckup, lost polling request".

"SEND FAILED: %s".

"SEND file "%s"".

"SEND: %s "%s", dirnum %d".

"SEND: %s (file %s, compression %d)".

"REJECT: %s".

"REJECT: %s, max remote page width %u, image width %lu".

"REJECT: %s, image resolution %g line/mm".

"REJECT: %s, max remote page length %d, image length %lu".

"REJECT: %s".

"STATE CHANGE: %s -> %s (timeout %ld)".

"STATE CHANGE: %s -> %s".

"ANSWER: FAX CONNECTION".

"ANSWER: DATA CONNECTION".

"ANSWER: Could not switch modem to data service".

"ANSWER: VOICE CONNECTION".

"ANSWER: %s".

"ANSWER: Can not lock modem device".

"GETTY: start pid %u,

"GETTY: terminated, exit status %#o".

"GETTY: could not create".

"GETTY: can not fork".

"runGetty::setregid: %m".

"runGetty::setreuid: %m".

"No support for XON/XOFF flow control with Class 1 driver".

"No support for RTS/CTS flow control with Everex driver".  

FAX PROTOCOL

The following messages may appear when the facsimile protocol tracing (bit 2) is enabled:

"%s: %s (Phase B)". An error occurred during Phase B of Group 3 protocol processing.

"DELAY %u ms". A %u-millisecond delay was done on the host.

"DIAL %s". The phone number %s was dialed. Note that this is the phone number passed as an argument to the ModemDialCmd parameter and so may not include additional dialing prefixes sent to the modem.

"Error sending T.30 prologue frames". An error occurred while trying to transmit the T.30 DCS frames.

"HDLC frame too short (%u bytes)". An HDLC protocol message was not at least 3 bytes long.

"HDLC frame with bad address field %#x". An HDLC protocol message was sent/received with an address field other than 0xff.

"HDLC frame with bad control field %#x". An HDLC protocol message was sent/received with an invalid control field.

"MODEM ERROR: %s". While waiting for a modem response/result an error was encountered (e.g. an ``ERROR'' result code).

"MODEM protocol botch (

"MODEM protocol botch, can not parse

"MODEM protocol botch: +FET: without +FPTS:".

"POLL: %s (begin)".

"POLL: %s (end)".

"POLL: begin".

"POLL: end".

"Problem receiving post-page HDLC frame".

"Problem sending TCF data".

"RECV PPM: %s".

"RECV PPR: %s".

"RECV interrupt request ignored".

"RECV training".

"RECV unknown PPM %#x".

"RECV: %d bytes of data".

"RECV: %lu bytes, %lu rows".

"RECV: %s (begin)".

"RECV: %s (end)".

"RECV: %s".

"RECV: TCF %u bytes, %u%% non-zero, %u zero-run".

"RECV: bad code word 0x%x, len %d, row %lu".

"RECV: begin".

"RECV: end".

"RECV: begin page".

"RECV: end page".

"RECV: premature EOF".

"RECV: row %lu, got EOL, eols %d".

"REMOTE %s PostScript transfer".

"REMOTE CSI

"REMOTE HANGUP: %s (code %s)".

"REMOTE NSF %#x".

"REMOTE NSS

"REMOTE TSI

"REMOTE best format %s".

"REMOTE best rate %s".

"REMOTE best vres %s".

"REMOTE has document to POLL".

"REMOTE max %s".

"REMOTE wants %s".

"SEND %s RTC", is2D ? "2D" : "1D".

"SEND begin page".

"SEND end page".

"SEND recv %s".

"SEND recv unknown FCF %#x".

"SEND training at %s".

"SEND training".

"SENT %u bytes of data".

"TRAINING failed".

"TRAINING succeeded".

"USE %s".

 

MODEM OPERATIONS

The following messages may appear when modem operation tracing (bit 3) is enabled:

"MODEM line set to %d baud (input XON/XOFF %s)". The DTE-DCE communication rate was set %d bits/sec on the host and software flow control for data received from the modem was either enabled or disabled.

"MODEM input XON/XOFF enabled". "MODEM input XON/XOFF disabled". Software flow control for data received from the modem was either enabled or disabled.

"<-- break". A break signal was sent to the modem. At present only the Everex modem driver sends breaks.

"TIMEOUT: %s modem". A timeout occurred while doing a modem-related operation; typically reading or writing data.

"Error #%u reading from modem". An error was returned by a read(2) system call. This usually happens when the modem prematurely drops the DCD signal.  

MODEM COMMUNICATION

The following messages may appear when modem communication tracing (bit 4) is enabled:

"--> [%d:%s]". A %d-byte line of data was received from the modem. Printable data are displayed.

"<-- data [%d]". %d bytes of unprintable data were sent to the modem, typically facsimile data.

"<-- [%d:%s]". %d bytes of printable data were sent to the modem. The data are displayed.  

TIMEOUTS

The following messages may appear when timeout tracing (bit 5) is enabled:

"start %d second timer". Start a %d-second timeout.

"stop timer". Stop the current timeout before it expires.

"stop timer - timer expired". The current timeout expired.  

HDLC FRAMES

When tracing of raw HDLC frames (bit 6) is enabled each frame sent and received is logged: "<-- HDLC<%u:%.*s>" for sent frames and "--> HDLC<%u:%.*s>" for received frames. These messages indicate that a %u-byte long HDLC frame was sent or received. The first byte should always be 0xff, the address field specified for dialup communication. The second byte should be a frame control field. The contents of the frame is displayed as sequence of bytes in hexadecimal.  

BINARY I/O

When binary input/output (bit 7) is traced there are two types of messages logged:

"<-- <%u:%.*s>" for data sent to the modem and "--> <%u:%.*s>" for data received from the modem. Each message indicates that %u bytes of data were transferred. The data is displayed as a sequence of bytes in hexadecimal.  

SEE ALSO

faxd(1M), config(4F)


 

Index

NAME
DESCRIPTION
SERVER OPERATION
FAX PROTOCOL
MODEM OPERATIONS
MODEM COMMUNICATION
TIMEOUTS
HDLC FRAMES
BINARY I/O
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 10:15:15 GMT, January 04, 2023